Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 8)

6. Planning and Implementing Mailbox Moves and Coexistence

This section examines the issues, recommendations, and requirements around migrating mailboxes to Exchange Server 2010 and coexisting with Exchange Server 2003 mailboxes.

6.1. Address List and E-mail Address Policy Filters

In Exchange Server 2003, filters for address lists and e-mail address policies were based on LDAP syntax; Exchange Server 2010 uses OPATH filtering syntax. Although LDAP syntax filters are supported in Exchange Server 2010, they must be upgraded to OPATH syntax if you want to edit them in Exchange Server 2010, and LDAP filters can't be created in Exchange Server 2010. In addition, LDAP filters cannot be upgraded to OPATH syntax with the EMC; they must be upgraded using the EMS.

6.1.1. Default Address List Filters

Although upgrading custom filters is essentially a manual process, the following cmdlets upgrade the default address lists from LDAP to OPATH filters:

• All Users default address list:

  Set-AddressList "All Users" -IncludedRecipients MailboxUsers

  
  

• All Groups default address list:

  Set-AddressList "All Groups" -IncludedRecipients MailGroups

  
  

• All Contacts default address list:

  Set-AddressList "All Contacts" -IncludedRecipients MailContacts

  
  

• Public Folders default address list:

  Set-AddressList "Public Folders" -RecipientFilter { RecipientType -eq
  'PublicFolder' }

  
  

• The Default Global Address List:

  Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne
  $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass
  -eq 'msExchSystemMailbox' -or ObjectClass -eq 'msExchDynamicDistributionList' -or
  ObjectClass -eq 'group' -or ObjectClass -eq 'publicFolder'))}
  
  					  

  
  

6.1.2. Custom Address List and E-mail Policy Filters

Custom filters for address lists, e-mail address policies, and dynamic distribution groups are a little more complicated to upgrade. Custom filters require you to determine what they are filtering for, and then translate the filter into OPATH syntax. The Microsoft Exchange Team has produced a script that will aid in converting most custom filters from LDAP to OPATH syntax; this script is available at http://msexchangeteam.com/archive/2007/03/12/436983.aspx. For any filters that must be upgraded manually, follow these steps:

This process is explained in more detail in the Exchange Server 2010 online help at http://technet.microsoft.com/en-us/library/cc164375.aspx.